home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
1994.11.gz
/
1994.11
/
000090_jp107@amtp.cam.ac.uk_Sun Nov 13 19:42:29 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-11-30
|
3KB
Received: from inn.amtp.cam.ac.uk by cs.umb.edu with SMTP id AA18287
(5.65c/IDA-1.4.4 for <tex-k@cs.umb.edu>); Sun, 13 Nov 1994 14:42:36 -0500
Return-Path: <J.S.Peatfield@damtp.cambridge.ac.uk>
Received: from club.amtp.cam.ac.uk [131.111.16.12] (TAP id = jp107)
by inn.amtp.cam.ac.uk with smtp
(Smail-3.1.28.1 #6) id m0r6koo-0001HfC; Sun, 13 Nov 94 19:42 GMT
Received: by club.amtp.cam.ac.uk (4.1/DAMTP 2.1-Client (club.amtp.cam.ac.uk MX-hub grey.amtp.cam.ac.uk))
id AA17040; Sun, 13 Nov 94 19:42:29 GMT
Date: Sun, 13 Nov 94 19:42:29 GMT
Message-Id: <9411131942.AA17040%club.amtp.cam.ac.uk@damtp.cambridge.ac.uk>
To: tex-k@cs.umb.edu
Subject: M in config.<printer>
From: Jon Peatfield <J.S.Peatfield@amtp.cam.ac.uk>
I just noticed that there has been a change in the way that the M
option in the config.<printer> is now interpretted since I last set up
dvips(k) on our machines.
Basically I think that when the -mode option was added the changes to
allow this to override the config.<printer> broke something else. The
result is that now dvips uses the *first* M option in any config file
it finds rather than the last as it previously did. I'd set up
config.ps to set defaults valid for most of our printers (M CanonCX),
and overrode this in the config.<printer> for those printers with
different engines. Now it sees the M CanonCX in the config.ps and
ignores the later ones as in resident.c it says:
> ...
> case 'M' :
> /* If we had the compilation default, replace it. But
> if they specified one with -mode, keep it. */
> if (!mfmode)
> mfmode = configstring(was_inline+1, 0) ;
> break ;
> ...
So it mfmode is set it never gets changed. I'd check the
mfmode_option variable here but this is local to main in dvips.c (the
*real* has the -mode been passed flag). I'd rather not move stuff
arround without letting other see if there is a better solution. In
the meantime I've altered our config.ps not to set M and set it in all
our config.<printer> files (tedius but correct.)
Any better suggestions? If not I'll post a patch in a couple of days.
(Not that I can be bothered to re-compile now I've fixed the problem
in the config-* files, but those CanonCX fonts being printed on our
ljfour's looked a little odd...)
In case I've missed it are there any other changes recently like this
which may cause the config.<printer> files to behave differently?
-- Jon
Jon Peatfield, Computer Officer, the DAMTP, University of Cambridge
Telephone: (+44 223) 3-37852 Mail: J.S.Peatfield@damtp.cam.ac.uk
Monotype Fonts. Get 'em while they're 'ot. On a Stick.